$ type MMS022.RELEASE_NOTES
 RELEASE NOTES FOR DEC/MMS V2.2



NEW FEATURES



      o  VAX DEC/MMS Version 2.2 includes support  for  the  VAX  Source
         Code   Analyzer   (SCA)  with  the  /SCA_LIBRARY[=library-name]
         command line qualifier.  When a source needs to be compiled and
         /SCA_LIBRARY  is  specified,  MMS  will direct the compilers to
         create .ANA files and will then load those files into  the  SCA
         Library.    The  following  languages  are  supported:   BASIC,
         BLISS-32, C, FORTRAN, PASCAL, and PL/I.

      o  An SCAFLAGS macro has been provided so that /LOG can be  turned
         off for the SCA commands.

      o  A method to determine if /SCA was specified on the command line
         has been added.  The macro SCALIBRARY will be undefined if /SCA
         was not specified.

      o  The  default  CMS  rule   has   been   changed   so   the   the
         /OUTPUT=filename      includes      a      file      extension.
         (/OUTPUT=filename.ext).

      o  In addition, the other default rules and flags macros have been
         changed  so  that  occurrances of $(MMS$TARGET_NAME) and $* are
         followed by the appropriate file extension.

      o  The  allowable  action  line  lengths  have   been   increased.
         Uncontinued   command   lines   have  grown  from  131  to  251
         characters.  When run under DCL, the maximum continued  command
         line  length  has  been  increased from 507 to 1019 characters.
         When  run  under  another  Command  Language  Interpreter,  VAX
         DEC/Shell  for  example, the limits are unchanged from previous
         versions.

      o  An MMS.DIR directory has been added to  [SYSHLP.EXAMPLES].   In
         this  directory  can  be  found  MMS' default rules in the file
         MMS$DEFAULT_RULES.MMS, and the default rules when  running  MMS
         under VAX DEC/SHELL in MMS$DEFAULT_SHELL_RULES.MMS.

      o  The User's Guide, now titled Guide to VAX DEC/Module Management
         System,  has been revised and expanded.  It contains additional
         information and many new examples.   The  Quick  Reference  has
         also been revised.




BUGS FIXED



    o  Previous versions of MMS did not fetch files  from  CMS  properly
       when  the  file  to  be  fetched  from  CMS was to be placed in a
       directory which was  not  the  current  default  directory.   For
       example,  the following dependency would cause the file TEST.C to
       be fetched to the current directory instead of directory [SOURCE]

       TEST.OBJ :  [SOURCE]TEST.C

       The default rule supplied with this version of MMS corrects  this
       problem.  The new default rule is:

       mms$cmslib :== 'f$trnlnm("CMS$LIB")
       IF mms$cmslib .nes. "$@" THEN $(CMS) SET LIBRARY $@
       $(CMS) FETCH $< /OUTPUT=$* $(CMSFLAGS) $(CMSCOMMENT)
       IF mms$cmslib .NES. "" .AND. mms$cmslib .NES. "$@" THEN -
       $(CMS) SET LIBRARY 'mms$cmslib'

    o  A problem has been fixed where if white space existed  after  the
       filename   specified   for   a  .MMS  INCLUDE  statement  in  the
       description file, attempting to Fetch the file from a CMS library
       would fail.

    o  In very rare  instances,  MMS  would  issue  the  GWKNOPRN  error
       message  (There  are  no  known  sources  for  the current target
       'target name.') when a source existed.  A single instance of this
       problem has been reported.  The problem has been fixed.

    o  MMS can now access .MMS files stored in CMS libraries which  have
       ACLs  set.   Part of this fix included removing several MMS error
       messages, and adding one.

    o  The following error messages have been removed:

       1.  LFSUNEXP,  Unexpected  error  from  RMS  while  looking   for
           'filespec'.

       2.  GMPRVIO, MMS does not have read access to 'filespec'.

       3.  LEXINACCRULE, Rules file 'filespec' is inaccessible.

       4.  LEXINACCINCL, Included file 'filespec' is inaccessible.

       5.  NODEPFIL,  Cannot  find  default  description  file   (either
           DESCRIP.MMS or MAKEFILE.).

       6.  NOSPECDEP, Cannot find specified description file 'filespec'.


    o  The following error messages have been added:

       1.  NOACCESS, Cannot access file 'filespec'
           The new message will be followed by a secondary message  from
           RMS providing a more complete explanation of the problem.

       2.  NOLIBSPECDBL, Library module specifications  not  allowed  as
           targets in double colon rules:  'target name'




RESTRICTIONS


    o  There are several restrictions associated with action lines.  See
       Action  Line  Restrictions  in  the  User's  Guide  for  detailed
       information.

    o  A file created by the /OUTPUT= qualifier from MMS  will  use  the
       user's default protection rather than any ACL on the directory in
       which the file is being created.

    o  Use of library module specifications as targets in  double  colon
       rules  is  disallowed.   A library module specification is one in
       which a source or target of a dependency rule is a  module  in  a
       VMS library, using the following format:

           library(module[=filespec],...)

       Instead of reporting "Internal MMS Error #2",  DEC/MMS  will  now
       report the new error message:

       NOLIBSPECDBL,  Library  module  specifications  not  allowed   as
       targets in double colon rules :  'target name.'

       For information concerning  working  around  the  library  module
       restriction, see the User's Guide.



WARNINGS


   1.  Any dependency rule whose action results in updating not only the
       given  target  for that rule, but another target in an MMS build,
       may have unpredictable results.

   2.  If a target appears in two  dependency  rules  in  a  description
       file,  and  action  lines are specified for both, the action line
       from the later dependency rule is used.   For  example,  see  the
       following description file:



                 FOO : BAR
                      action one
                 FOO : BAR BAS
                      action two


       If the file FOO needs updating, then the second  action  will  be
       performed, and the first action will be discarded.


$ 
